Replace sbt-extras with direct sbt launcher installation #291
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Malax
force-pushed
the
malax/sbt-launcher-improvements
branch
7 times, most recently
from
022a131 to
a751cda
Compare
Malax
force-pushed
the
malax/sbt-launcher-improvements
branch
from
a751cda to
52fb9e0
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This replaces the sbt-extras wrapper script with a simpler approach that downloads and verifies the sbt launcher jar directly from Maven Central (or Typesafe Ivy for 0.x versions).
The new implementation:
The sbt global directory is now recreated on each build to ensure plugins are always current.